Summary

Describe the change.

What Changed

Key files and behaviors.

Validation

How you tested.

Risks

Anything to watch.

Greptile Summary

This PR introduces a pending-image-attachment UX: while clipboard or file images are being saved to disk, the attachment tray shows a cancellable thumbnail so the send button is disabled until the save completes. A new appSaveClipboardImageAttachment IPC handler reads the Electron clipboard, writes the PNG to .ade/attachments/, and returns a downsized 96×96 preview, avoiding the previous pattern of routing the full base64 payload through the renderer.

• New IPC handler (appSaveClipboardImageAttachment): reads clipboard PNG in the main process, saves it with the shared saveAgentChatTempAttachmentBuffer helper, and returns a compact preview data URL instead of the full image bytes.
• Pending-attachment state (pendingImageAttachments, imagePreviewUrls): composer tracks in-flight saves; ChatAttachmentTray renders a PendingImageAttachmentPreview spinner with a blob-URL thumbnail while the temp file write is in progress.
• Preview seeding: once a save completes, the resulting ImageAttachmentPreview receives the already-computed URL as initialPreviewUrl, skipping the async getImageDataUrl IPC round-trip entirely.

Confidence Score: 5/5

Safe to merge — no functional regressions identified; the pending-attachment flow is guarded correctly at every async boundary.

The new IPC handler and React state machinery are each internally consistent. The cancellation ref is checked after every await, the object URL lifecycle is managed through effects with correct prev/current diffing, and the composerInputLocked effect's early-return guard prevents the pendingImageAttachments dep from causing spurious cancellations. The one suggestion is a dep-array tidyup that doesn't change runtime behavior.

No files require special attention; the most complex logic is in AgentChatComposer.tsx but its pending-attachment state machine is well-tested by the new test cases.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant User
    participant Renderer as AgentChatComposer
    participant Tray as ChatAttachmentTray
    participant Main as Main Process (IPC)
    participant FS as Filesystem

    User->>Renderer: Cmd+V / Paste / Drop image
    Renderer->>Renderer: addPendingImageAttachment()
    Renderer->>Tray: render PendingImageAttachmentPreview

    alt Native clipboard path
        Renderer->>Main: IPC: appSaveClipboardImageAttachment
        Main->>FS: writeFile(.ade/attachments/uuid.png)
        Main->>Main: image.resize(96x96) toDataURL()
        Main-->>Renderer: path + previewDataUrl
    else File-backed path
        Renderer->>Renderer: createObjectURL(file)
        Renderer->>Main: IPC: agentChatSaveTempAttachment
        Main->>FS: writeFile(.ade/attachments/uuid.ext)
        Main-->>Renderer: path
    end

    Renderer->>Renderer: onAddAttachment + dropPendingImageAttachment
    Renderer->>Tray: render ImageAttachmentPreview with initialPreviewUrl

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
apps/desktop/src/renderer/components/chat/AgentChatComposer.tsx:1103-1111
Adding `pendingImageAttachments` to the dependency array causes this effect to fire on every pending-attachment state change (every add and every drop), even though the `!composerInputLocked` guard makes each of those extra runs a no-op. Moving the ref-population into the functional state-setter eliminates the closure dependency entirely, so the dep array can stay as `[composerInputLocked]` and the effect only fires on lock transitions.

```suggestion
    clipboardImagePasteFallbackAttachedRef.current = false;
    setPendingImageAttachments((current) => {
      for (const attachment of current) {
        cancelledPendingImageAttachmentsRef.current.add(attachment.id);
      }
      return current.length ? [] : current;
    });
  }, [composerInputLocked]);
```

_{Reviews (2): Last reviewed commit: "ship: iteration 1 - address pasted image..." | Re-trigger Greptile}